|
Showing 1 - 16 of
16 matches in All Departments
As software RandD investment increases, the benefits from short
feedback cycles using technologies such as continuous deployment,
experimentation-based development, and multidisciplinary teams
require a fundamentally different strategy and process. This book
will cover the three overall challenges that companies are
grappling with: speed, data and ecosystems. Speed deals with
shortening the cycle time in RandD. Data deals with increasing the
use of and benefit from the massive amounts of data that companies
collect. Ecosystems address the transition of companies from being
internally focused to being ecosystem oriented by analyzing what
the company is uniquely good at and where it adds value.
As software R&D investment increases, the benefits from short
feedback cycles using technologies such as continuous deployment,
experimentation-based development, and multidisciplinary teams
require a fundamentally different strategy and process. This book
will cover the three overall challenges that companies are
grappling with: speed, data and ecosystems. Speed deals with
shortening the cycle time in R&D. Data deals with increasing
the use of and benefit from the massive amounts of data that
companies collect. Ecosystems address the transition of companies
from being internally focused to being ecosystem oriented by
analyzing what the company is uniquely good at and where it adds
value.
This book provides essential insights on the adoption of modern
software engineering practices at large companies producing
software-intensive systems, where hundreds or even thousands of
engineers collaborate to deliver on new systems and new versions of
already deployed ones. It is based on the findings collected and
lessons learned at the Software Center (SC), a unique collaboration
between research and industry, with Chalmers University of
Technology, Gothenburg University and Malmoe University as academic
partners and Ericsson, AB Volvo, Volvo Car Corporation, Saab
Electronic Defense Systems, Grundfos, Axis Communications, Jeppesen
(Boeing) and Sony Mobile as industrial partners. The 17 chapters
present the "Stairway to Heaven" model, which represents the
typical evolution path companies move through as they develop and
mature their software engineering capabilities. The chapters
describe theoretical frameworks, conceptual models and, most
importantly, the industrial experiences gained by the partner
companies in applying novel software engineering techniques. The
book's structure consists of six parts. Part I describes the model
in detail and presents an overview of lessons learned in the
collaboration between industry and academia. Part II deals with the
first step of the Stairway to Heaven, in which R&D adopts agile
work practices. Part III of the book combines the next two phases,
i.e., continuous integration (CI) and continuous delivery (CD), as
they are closely intertwined. Part IV is concerned with the highest
level, referred to as "R&D as an innovation system," while Part
V addresses a topic that is separate from the Stairway to Heaven
and yet critically important in large organizations: organizational
performance metrics that capture data, and visualizations of the
status of software assets, defects and teams. Lastly, Part VI
presents the perspectives of two of the SC partner companies. The
book is intended for practitioners and professionals in the
software-intensive systems industry, providing concrete models,
frameworks and case studies that show the specific challenges that
the partner companies encountered, their approaches to overcoming
them, and the results. Researchers will gain valuable insights on
the problems faced by large software companies, and on how to
effectively tackle them in the context of successful cooperation
projects.
The success of product line engineering techniques in the last 15
years has popularized the use of software variability as a key
modeling approach for describing the commonality and variability of
systems at all stages of the software lifecycle. Software product
lines enable a family of products to share a common core platform,
while allowing for product specific functionality being built on
top of the platform. Many companies have exploited the concept of
software product lines to increase the resources that focus on
highly differentiating functionality and thus improve their
competitiveness with higher quality and reusable products and
decreasing the time-to-market condition. Many books on product line
engineering either introduce specific product line techniques or
include brief summaries of industrial cases. From these sources, it
is difficult to gain a comprehensive understanding of the various
dimensions and aspects of software variability. Here the editors
address this gap by providing a comprehensive reference on the
notion of variability modeling in the context of software product
line engineering, presenting an overview of the techniques proposed
for variability modeling and giving a detailed perspective on
software variability management. Their book is organized in four
main parts, which guide the reader through the various aspects and
dimensions of software variability. Part 1 which is mostly written
by the editors themselves introduces the major topics related to
software variability modeling, thus providing a multi-faceted view
of both technological and management issues. Next, part 2 of the
book comprises four separate chapters dedicated to research and
commercial tools. Part 3 then continues with the most practical
viewpoint of the book presenting three different industry cases on
how variability is managed in real industry projects. Finally, part
4 concludes the book and encompasses six different chapters on
emerging research topics in software variability like e.g.
service-oriented or dynamic software product lines, or variability
and aspect orientation. Each chapter briefly summarizes "What you
will learn in this chapter", so both expert and novice readers can
easily locate the topics dealt with. Overall, the book captures the
current state of the art and best practices, and indicates
important open research challenges as well as possible pitfalls.
Thus it serves as a reference for researchers and practitioners in
software variability management, allowing them to develop the next
set of solutions, techniques and methods in this complicated and
yet fascinating field of software engineering.
This book provides essential insights on the adoption of modern
software engineering practices at large companies producing
software-intensive systems, where hundreds or even thousands of
engineers collaborate to deliver on new systems and new versions of
already deployed ones. It is based on the findings collected and
lessons learned at the Software Center (SC), a unique collaboration
between research and industry, with Chalmers University of
Technology, Gothenburg University and Malmoe University as academic
partners and Ericsson, AB Volvo, Volvo Car Corporation, Saab
Electronic Defense Systems, Grundfos, Axis Communications, Jeppesen
(Boeing) and Sony Mobile as industrial partners. The 17 chapters
present the "Stairway to Heaven" model, which represents the
typical evolution path companies move through as they develop and
mature their software engineering capabilities. The chapters
describe theoretical frameworks, conceptual models and, most
importantly, the industrial experiences gained by the partner
companies in applying novel software engineering techniques. The
book's structure consists of six parts. Part I describes the model
in detail and presents an overview of lessons learned in the
collaboration between industry and academia. Part II deals with the
first step of the Stairway to Heaven, in which R&D adopts agile
work practices. Part III of the book combines the next two phases,
i.e., continuous integration (CI) and continuous delivery (CD), as
they are closely intertwined. Part IV is concerned with the highest
level, referred to as "R&D as an innovation system," while Part
V addresses a topic that is separate from the Stairway to Heaven
and yet critically important in large organizations: organizational
performance metrics that capture data, and visualizations of the
status of software assets, defects and teams. Lastly, Part VI
presents the perspectives of two of the SC partner companies. The
book is intended for practitioners and professionals in the
software-intensive systems industry, providing concrete models,
frameworks and case studies that show the specific challenges that
the partner companies encountered, their approaches to overcoming
them, and the results. Researchers will gain valuable insights on
the problems faced by large software companies, and on how to
effectively tackle them in the context of successful cooperation
projects.
|
Software Architecture: System Design, Development and Maintenance - 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture (WICSA3), August 25-30, 2002, Montreal, Quebec, Canada (Paperback, Softcover reprint of the original 1st ed. 2002)
Jan Bosch, Morven Gentleman, Christine Hofmeister, Juha Kuusela
|
R4,473
Discovery Miles 44 730
|
Ships in 10 - 15 working days
|
For more and more systems, software has moved from a peripheral to
a central role, replacing mechanical parts and hardware and giving
the product a competitive edge. Consequences of this trend are an
increase in: the size of software systems, the variability in
software artifacts, and the importance of software in achieving the
system-level properties. Software architecture provides the
necessary abstractions for managing the resulting complexity. We
here introduce the Third Working IEEFlIFIP Conference on Software
Architecture, WICSA3. That it is already the third such conference
is in itself a clear indication that software architecture
continues to be an important topic in industrial software
development and in software engineering research. However, becoming
an established field does not mean that software architecture
provides less opportunity for innovation and new directions. On the
contrary, one can identify a number of interesting trends within
software architecture research. The first trend is that the role of
the software architecture in all phases of software development is
more explicitly recognized. Whereas initially software architecture
was primarily associated with the architecture design phase, we now
see that the software architecture is treated explicitly during
development, product derivation in software product lines, at
run-time, and during system evolution. Software architecture as an
artifact has been decoupled from a particular lifecycle phase.
This volume constitutes the refereed proceedings of the 14th
International Software Product Line Conference, SPLC 2010, held on
Jeju Island, South Korea, in September 2010.
|
Software Reuse: Methods, Techniques, and Tools - 8th International Conference, ICSR 2004, Madrid, Spain, July 5-9, 2004, Proceedings (Paperback, 2004 ed.)
Jan Bosch, Charles Krueger
|
R1,694
Discovery Miles 16 940
|
Ships in 10 - 15 working days
|
Afterthree decadesofresearch andpractice, reuse
ofexistingsoftwareartefactsremains the most promising approach to
decreasing effort for software development and evo- tion,
increasing quality of software artefacts and decreasing time to
market of software products. Over time, we have seen impressive
improvements, in extra-organizational reuse, e.g.COTS,
aswellasinintra-organizationalreuse, e.g.softwareproductfamilies.
Despite the successes that we, as a community, have achieved,
several challenges remain to be addressed. The theme for this
eighth meeting of the premier international conference on software
reuse is the management of software variability for reusable
software.Allreusablesoftwareoperatesinmultiplecontextsandhastoaccommodatethe
differencesbetweenthesecontextsthroughvariation.Inmodernsoftware,
thenumberof variation points may range in the thousands with an
even larger number of dependencies between these points. Topics
addressing the theme include the representation, design, assessment
and evolution of software variability. The proceedings that you are
holding as you read this report on the current state-- the-art in
software reuse.Topics covered in the proceedings include software
variability, testing of reusable software artefacts, feature
modeling, aspect-oriented software de- lopment, composition of
components and services, model-based approaches and several other
aspects of software reuse. May 2004 Jan Bosch Charles Krueger
Organizing Committee General Chair Kyo C. Kang, Pohang University
of Science and Technology, Korea Program Co-chairs Jan Bosch,
University of Groningen, The Netherlands Charles Krueger, BigLever
Software, Inc., U
|
Software Architecture: System Design, Development and Maintenance - 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture (WICSA3), August 25-30, 2002, Montreal, Quebec, Canada (Hardcover, 2002 ed.)
Jan Bosch, Morven Gentleman, Christine Hofmeister, Juha Kuusela
|
R4,641
Discovery Miles 46 410
|
Ships in 10 - 15 working days
|
For more and more systems, software has moved from a peripheral to
a central role, replacing mechanical parts and hardware and giving
the product a competitive edge. Consequences of this trend are an
increase in: the size of software systems, the variability in
software artifacts, and the importance of software in achieving the
system-level properties. Software architecture provides the
necessary abstractions for managing the resulting complexity. We
here introduce the Third Working IEEFlIFIP Conference on Software
Architecture, WICSA3. That it is already the third such conference
is in itself a clear indication that software architecture
continues to be an important topic in industrial software
development and in software engineering research. However, becoming
an established field does not mean that software architecture
provides less opportunity for innovation and new directions. On the
contrary, one can identify a number of interesting trends within
software architecture research. The first trend is that the role of
the software architecture in all phases of software development is
more explicitly recognized. Whereas initially software architecture
was primarily associated with the architecture design phase, we now
see that the software architecture is treated explicitly during
development, product derivation in software product lines, at
run-time, and during system evolution. Software architecture as an
artifact has been decoupled from a particular lifecycle phase.
This book constitutes the refereed proceedings of the Third International Conference on Generative and Component-Based Software Engineering, GCSE 2001, held in Erfurt, Germany, in September 2001.The 14 revised full papers presented together with one invited paper were carefully reviewed and selected from 43 submissions. The papers are organized in topical sections on software product lines, aspects, generic and generative approaches, and components and architectures.
At the time of writing (mid-October 1998) we can look back at what
has been a very successful ECOOP'98. Despite the time of the year -
in the middle of what is traditionally regarded as a holiday period
- ECOOP'98 was a record breaker in terms of number of participants.
Over 700 persons found their way to the campus of the Brussels Free
University to participate in a wide range of activities. This 3rd
ECOOP workshop reader reports on many of these activities. It
contains a careful selection of the input and a cautious summary of
the outcome for the numerous discussions that happened during the
workshops, demonstrations and posters. As such, this book serves as
an excellent snapshot of the state of the art in the field of
object oriented programming. About the diversity of the submissions
A workshop reader is, by its very nature, quite diverse in the
topics covered as well as in the form of its contributions. This
reader is not an exception to this rule: as editors we have given
the respective organizers much freedom in their choice of
presentation because we feel form follows content. This explains
the diversity in the types of reports as well as in their lay out.
Jan Bosch Stuart Mitchell University of Karlskrona/Ronneby
University of York Dept of Computer Science Dept of Computer
Science SoftCenter, S-372 25, Ronneby, Sweden York, United Kingdom
[email protected] [email protected] 1 Introduction
Although becoming more accepted in software industry,
object-oriented technology still is an active ?eld of research with
many issues remaining to be addressed. This workshop reader, in a
way, presents the width of the ongoing research activities in
object-orientation. However, we feel one can classify these
activities into three cate- ries: * Domain-speci?c: Several
activities focus on a single application, e.g. telec- munication,
or computer-science, e.g. real-time and mobility, domain. Research
tries to address the domain-speci?c problems of object-oriented
technology. * Design issues: Object-oriented design has been an
issue for at least a decade, but one can identify an increasing
focus on formal approaches and on the evo- tion and re-engineering
of existing object-oriented software. * Beyond object-orientation:
The object-oriented paradigm will, at some point, be replaced by a
subsequent paradigm and several research efforts investigate
alternative or extended approaches. Examples are extended language
expr- siveness for, e.g. design patterns and frameworks,
component-oriented p- gramming and aspect-oriented programming. 2
Contents The remainder of this book is a selection and re-iteration
of the contributions to 12 workshops (of a total of 15) held during
the ECOOP'97 conference. The workshops generally relate to one of
the above categories.
This book celebrates the 10-year anniversary of Software Center (a
collaboration between 18 European companies and five Swedish
universities) by presenting some of the most impactful and relevant
journal or conference papers that researchers in the center have
published over the last decade. The book is organized around the
five themes around which research in Software Center is organized,
i.e. Continuous Delivery, Continuous Architecture, Metrics,
Customer Data and Ecosystems Driven Development, and AI
Engineering. The focus of the Continuous Delivery theme is to help
companies to continuously build high quality products with the
right degree of automation. The Continuous Architecture theme
addresses challenges that arise when balancing the need for
architectural quality and more agile ways of working with shorter
development cycles. The Metrics theme studies and provides insight
to understand, monitor and improve software processes, products and
organizations. The fourth theme, Customer Data and Ecosystem Driven
Development, helps companies make sense of the vast amounts of data
that are continuously collected from products in the field.
Eventually, the theme of AI Engineering addresses the challenge
that many companies struggle with in terms of deploying machine-
and deep-learning models in industrial contexts with production
quality. Each theme has its own part in the book and each part has
an introduction chapter and then a carefully selected reprint of
the most important papers from that theme. This book mainly aims at
researchers and advanced professionals in the areas of software
engineering who would like to get an overview about the achievement
made in various topics relevant for industrial large-scale software
development and management - and to see how research benefits from
a close cooperation between industry and academia.
This Book Is In Dutch. Due to the very old age and scarcity of this
book, many of the pages may be hard to read due to the blurring of
the original text.
This Book Is In Dutch. Due to the very old age and scarcity of this
book, many of the pages may be hard to read due to the blurring of
the original text.
|
|